Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove YSU theta -> t -> theta tendency computations #10

Open
wants to merge 1 commit into
base: myMPAS-v7.0.bl_ysu_condensates
Choose a base branch
from

Conversation

davegill
Copy link
Collaborator

At the end of the ysu subroutine, this mod removes the computation
that switches the temperature tendency to a potential temperature
tendency.

We make that change because inside of the bl_ysu_run subroutine, we
removed the computation that changed the potential temperature
tendency to a temperature tendency.

At the end of the bl_ysu_run routine, we have a potential temperature
tendency. There is no need to temporarily convert this to a temperature
tendency, only to reconvert it back to a potential temperature
tendency immediately after the routine exits.

As expected, this change causes bit-for-bit differences. This change
was not included in the sequence of ysu mods that give bit-wise identical
results so as to allow the far larger code modifications to be validated
more easily.

Both MPAS and WRF physics developers OK'ed this modification. Both
MPAS and WRF physics schemes expect to handle potential temperature
tendencies coming out of the PBL scheme from phyics.

Advantages:

  1. No need to do reciprocal computations to get back to the same
    state variable (algebraically the same).
  2. The trailing computation in the ysu scheme (which is now removed)
    would have required an extra CPF interstitial routine.

modified: src/core_atmosphere/physics/physics_sima/bl_ysu.F

At the end of the ysu subroutine, this mod removes the computation
that switches the temperature tendency to a potential temperature
tendency.

We make that change because inside of the bl_ysu_run subroutine, we
removed the computation that changed the potential temperature
tendency to a temperature tendency.

At the end of the bl_ysu_run routine, we have a potential temperature
tendency. There is no need to temporarily convert this to a temperature
tendency, only to reconvert it back to a potential temperature
tendency immediately after the routine exits.

As expected, this change causes bit-for-bit differences. This change
was not included in the sequence of ysu mods that give bit-wise identical
results so as to allow the far larger code modifications to be validated
more easily.

Both MPAS and WRF physics developers OK'ed this modification. Both
MPAS and WRF physics schemes expect to handle potential temperature
tendencies coming out of the PBL scheme from phyics.

Advantages:
1. No need to do reciprocal computations to get back to the same
state variable (algebraically the same).
2. The trailing computation in the ysu scheme (which is now removed)
would have required an extra CPF interstitial routine.

modified:   src/core_atmosphere/physics/physics_sima/bl_ysu.F
ldfowler58 pushed a commit that referenced this pull request Jun 7, 2022
KEYWORDS: halo exchange, adjoint 

DESCRIPTION OF CHANGES:
* This is a companion of JCSDA/mpas-jedi#361 .
* `stream_function` and `velocity_potential` are added to Registry as a `jedi-da` package.
* Adjoint of halo exchange is added (`mpas_dmpar_exch_halo_adj_field`). Only `mpas_dmpar_exch_halo_adj_field2d_real` was written because this is what is really used in JCSDA/mpas-jedi#361 .  

LIST OF MODIFIED FILES:
M       src/core_atmosphere/Registry.xml
M       src/framework/mpas_dmpar.F
ldfowler58 pushed a commit that referenced this pull request Jun 7, 2022
This alters the signature of the mpas_init subroutine in mpas_subdriver.F, adding two optional parameters that allow the caller to pass in filenames for the namelist and streams file. This allows the caller to specify different files to be used, other than namelist.atmosphere and streams.atmosphere in the working directory. This functionality is critical for several use-cases in MPAS-JEDI, including the ConvertState application, which interpolates data between two MPAS meshes of different resolutions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant